Systems and methods for providing cross-device native functionality in a mobile-based crowdsourcing platform

ABSTRACT

The present invention provides systems and methods for providing cross-device native functionality for a native app. More specifically, the invention is directed to a JavaScript Object Notation (JSON) data exchange format for use with a native app running on a user&#39;s mobile device, wherein the exchange format is configured to improve user experience and interaction with the app. The present invention may be particularly useful in a mobile-based crowdsourcing platform in which data is continually exchanged between remote user devices and a cloud-based service for collecting and managing user-driven data based on user interaction with native apps on their devices.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 14/328,492, filed Jul. 10, 2014, which claims the benefit ofU.S. Provisional Application No. 61/903,123, filed Nov. 12, 2013, andU.S. Provisional Application No. 61/844,494, filed Jul. 10, 2013.

This application claims the benefit of U.S. Provisional Application No.62/189,446, filed Jul. 7, 2015, and U.S. Provisional Application No.62/189,448, filed Jul. 7, 2015, and U.S. Provisional Application No.62/189,451, filed Jul. 7, 2015.

The contents of each of related applications previously noted areincorporated by reference herein in their entireties.

FIELD OF THE INVENTION

The present disclosure relates generally to management systems andmethods, and, more particularly, to a system for providing amobile-based crowdsourcing platform configured to provide an intuitiveand semi-automated means of collecting and managing user-driven data.

BACKGROUND

Mobile applications, also known as “apps”, offer application programminginterfaces (APIs) for accessing, for example, internet services, devicesensors for a device on which an application is installed, userinterface (UI) components, and the like. The applications can bepre-installed on mobile devices during manufacture, downloaded bycustomers from various mobile software distribution platforms, orinclude web applications delivered over Hypertext Transfer Protocol(HTTP), for example. Due to differences in device platforms,applications may be written or deployed in native application code thatis specific to a particular platform. A native application (referred toherein as “native app”) is an application program that has beendeveloped for use on a particular platform or device. Because nativeapps are written for a specific platform, they can interact with andtake advantage of operating system features and other software that istypically installed on that platform. Furthermore, a native app has theability to use device-specific hardware and software, meaning thatnative apps can take advantage of the latest technology available onmobile devices, such as a global positioning system (GPS), camera, orother sensor components. This can be construed as an advantage fornative apps over Web apps or mobile cloud apps.

In order to realize any periodic modifications in applications, theapplications need to be updated for each modification. However, thisaspect has been known to limit the speed of development and deploymentof new applications across different platforms. More specifically, intoday's current app-centric environment, there are a number ofchallenges facing companies to deploy apps or updates to their existingapps. Some of the challenges include updating user interface (UI)elements mandates. For example, developers may need to push updates to auser's device, which generally results in disruption to the user (e.g.,requires user to install update and interrupt regular use of theirdevice) and further requires users to constantly download new updates asthey occur. Some developers utilize hybrid apps. A hybrid app is onethat combines elements of both native and Web applications. However,hybrid apps are not entirely user friend and rely on internetconnectivity, which can be limiting.

Other challenges include cross-platform native capability (e.g., abilityof software to be run on more than one platform with little or nospecial preparation). The term platform can refer to the type ofprocessor and/or other hardware on which a given operating system orapplication runs, the type of operating system on a computer, or thecombination of the type of hardware and the type of operating systemrunning on it. In the context of mobile devices (e.g., smartphones), anapplication may need to be written in a particular format to match theplatform of any given device (e.g., iOS, Android, Windows, etc.).

In order to address cross-platform issues, some companies have relied oncommon language compilers that compile a piece of code into native form.However, any updates to the app still require a push, and thus result inthe drawbacks previously described. Some companies may utilize a hybridapp for providing cross-platform capability. The use of a hybrid appgenerally involves the use of a wrapper, such as PHONE GAP. A wrapper isessentially a mobile development framework for allowing programmers tobuild apps using programming languages, such as JavaScript, HTML, CSS,instead of relying on a platform-specific APIs such as those in iOS,Android, or Windows. The resulting applications are hybrid, meaning thatthey are neither truly native mobile application (because all layoutrendering is done via web views instead of the platform's native UIframework) nor purely web-based (because they are not just web apps, butare packaged as apps for distribution and have access to native deviceAPIs). A drawback of using hybrid apps is that they do not provide arobust offline capability and further provide a subpar user experience.

SUMMARY

The present invention provides systems and methods for providingcross-device native functionality for a native app. More specifically,the invention is directed to a JavaScript Object Notation (JSON) dataexchange format for use with a native app running on a user's mobiledevice, wherein the exchange format is configured to improve userexperience and interaction with the app. The present invention may beparticularly useful in a mobile-based crowdsourcing platform in whichdata is continually exchanged between remote user devices and acloud-based service for collecting and managing user-driven data basedon user interaction with native apps on their devices. However, itshould be noted that the present invention is not limited to use in acrowdsourcing platform scenario, and may be implemented in mobileapplications (apps) in general and not directed to crowdsourcing. Forexample, the JSON data exchange format may be implemented in a nativeapp directed to providing surveys to a user, or to provide a user with aview and/or control over sensor data in a building, or generating amodule available upon demand for entering the cost of a particular workorder on the fly. The uses of the JSON data exchange format of thepresent invention are limitless.

The present invention generally provides a system including a pluralityof remote mobile devices configured to communicate and exchange datawith a cloud-based service, such as a crowdsourcing platform. Each ofthe plurality of mobile devices is generally running an abstractednative app for allowing a user to interact and share data with thecloud-based service. The abstracted native app generally includes an appshell, native basic UI elements, and a JSON Translator embedded withinthe app configured to dynamically and, in real time (when connected tothe cloud-based service), translate objects received from thecloud-based service to native UI elements. Accordingly, the JSONTranslator acts as a translation layer allowing the dynamicinterpretation of data (e.g., app updates) received from cloud-basedservice into native UI elements compatible with the native app runningon the device. Thus, the data exchange format of the present inventionallows streaming of UI changes, in contrast to requiring a developer tospecifically write the language into a compatible format in eachinstance of an update. The cloud-based service includes componentsconfigured to allow the distribution of the objects to the mobiledevices and further allows administrators to make changes ormodifications to the app. The system allows an administrator (e.g.,customer or client providing service) to make changes or modificationsto an app in a mobile device's native form on the fly without requiringa re-download or an update of the app.

The present invention provides numerous advantages over current systems.In particular, the novel data exchange format allows for the control ofuser experience and the UI elements without forcing app updates,essentially allowing an administrator or app owner/developer to controlwhat the user can and cannot do on the app. Furthermore, the mobile appis in native form, which provides optimal user experience, as a userneed only download and install the native app once and any updates areseamlessly transmitted thereto without requiring re-download oradditional installs. The present invention further simplifies thedevelopment process for light weight native apps, which willsignificantly reduce time for entry to market. The present inventionfurther improves host of capabilities, such as automated workflow andautomated UI interaction, as well as potentially expanding thelocalization capabilities.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the claimed subject matter will be apparentfrom the following detailed description of embodiments consistenttherewith, which description should be considered with reference to theaccompanying drawings.

FIG. 1 is a block diagram illustrating one embodiment of an exemplarysystem for providing cross-device native functionality for a native app.

FIG. 2 is a block diagram illustrating the server of FIG. 1 in greaterdetail.

FIG. 3 is a block diagram illustrating at least one embodiment of amobile device for running a native app consistent with the presentdisclosure.

FIG. 4 is a block diagram illustrating the app management systemprovided by a server in greater detail.

FIG. 5 is a block diagram illustrating streaming of UI changes to amobile device consistent with the present disclosure.

FIGS. 6A-6C illustrate the streaming of app modification data to themobile device and subsequent dynamic interpretation and translation ofapp modification by the translation layer of the mobile device intonative UI elements for display to a user.

FIG. 7 is a block diagram illustrating one embodiment of systemarchitecture consistent with the present disclosure.

For a thorough understanding of the present disclosure, reference shouldbe made to the following detailed description, including the appendedclaims, in connection with the above-described drawings. Although thepresent disclosure is described in connection with exemplaryembodiments, the disclosure is not intended to be limited to thespecific forms set forth herein. It is understood that various omissionsand substitutions of equivalents are contemplated as circumstances maysuggest or render expedient.

DETAILED DESCRIPTION

By way of overview, the present invention provides systems and methodsfor providing cross-device native functionality for a native app. Morespecifically, the invention is directed to a JavaScript Object Notation(JSON) data exchange format for use with a native app running on auser's mobile device, wherein the exchange format is configured toimprove user experience and interaction with the app.

The following description includes exemplary embodiments of the presentinvention implemented in a mobile-based crowdsourcing platform. Asdescribed in greater detail herein, the JSON data exchange format in anative app may be particularly useful in a mobile-based crowdsourcingplatform in which data is continually exchanged between remote userdevices and a cloud-based service for collecting and managinguser-driven data based on user interaction with native apps on theirdevices. It should be noted, however, that the present invention is notlimited to use in a crowdsourcing platform scenario, and may beimplemented in mobile applications (apps) in general and not directed tocrowdsourcing. For example, the JSON data exchange format may beimplemented in a native app directed to providing surveys to a user, orto provide a user with a view and/or control over sensor data in abuilding, or generating a module available upon demand for entering thecost of a particular work order on the fly. The uses of the JSON dataexchange format of the present invention are limitless.

The present invention generally provides a system including a pluralityof remote mobile devices configured to communicate and exchange datawith a cloud-based service, such as a crowdsourcing platform. Each ofthe plurality of mobile devices is generally running an abstractednative app for allowing a user to interact and share data with thecloud-based service. The abstracted native app generally includes an appshell, native basic UI elements, and a JSON Translator embedded withinthe app configured to dynamically and, in real time (when connected tothe cloud-based service), translate objects received from thecloud-based service to native UI elements. Accordingly, the JSONTranslator acts as a translation layer allowing the dynamicinterpretation of data (e.g., app updates) received from cloud-basedservice into native UI elements compatible with the native app runningon the device. Thus, the data exchange format of the present inventionallows streaming of UI changes, in contrast to requiring a developer tospecifically write the language into a compatible format in eachinstance of an update. The cloud-based service includes componentsconfigured to allow the distribution of the objects to the mobiledevices and further allows administrators to make changes ormodifications to the app. The system allows an authorized user, such asan administrator, customer, or client providing service) to make changesor modifications to an app in a mobile device's native form on the flywithout requiring a re-download or an update of the app.

Accordingly, the present invention provides numerous advantages overcurrent systems. In particular, the novel data exchange format allowsfor the control of user experience and the UI elements without forcingapp updates, essentially allowing an administrator or appowner/developer to control what the user can and cannot do on the app.Furthermore, the mobile app is in native form, which provides optimaluser experience. The present invention further simplifies thedevelopment process for light weight native apps, which willsignificantly reduce time for entry to market. The present inventionfurther improves host of capabilities, such as automated workflow andautomated UI interaction, as well as potentially expanding thelocalization capabilities.

FIG. 1 illustrates one embodiment of an exemplary system 10 consistentwith the present disclosure. As shown, the system 10 includes a server12 embodied on an internet-based computing system/service. For example,as shown, the server 12 may be embodied on a cloud-based service 14, forexample. The server 12 is configured to communicate and share data withone or more users 15(1)-15(n) via user mobile devices 16(a)-16(n) over anetwork 18. In the present context, the users 15(1)-15(n) may includeadministrators, customers, developers, or clients of a service providedto one or more members of the public via the server 12. The users15(1)-15(n) may also include particular persons to which the service isdirected.

For example, the server 12 may host a crowdsourcing platform forreceiving user-driven data related to a particular environment in whichusers may be located, or otherwise reside, wherein such data may beuseful to an owner of the space. In one example, the crowdsourcingplatform may be useful in building maintenance, wherein the server isconfigured to collect data from patrons or employees within a space,such as an office space, wherein such data may be related to comfortissues such as HVAC (e.g., temperature of a particular room within abuilding), building maintenance issues (e.g., lighting issues,cleanliness of facilities, etc.), as well as other aspects of a buildingor space that may be useful in management of such space. Accordingly,the system of the present invention may include the crowdsourcingplatform as described in co-pending and co-owned U.S. patent applicationSer. No. 14/328,492, filed Jul. 10, 2014, the content of which isincorporated by reference herein in its entirety.

The system 10 may further include an external computing system/server 22configured to communicate with at least the cloud-based service 14, andsubsequently the server 12, via the network 18. The external computingsystem/server 20 may be embodied as a remote server, for example, forcommunicating with the server 12 and for performing the other functionsdescribed herein. Similarly, in some embodiments, the server 12 may beembodied on the external computing system/server 22. In the embodimentsdescribed herein, the external computing system/server 20 may beembodied as a remote server having one or more databases associated withthe server 12, as will be described in greater detail herein.

The network 18 may represent, for example, a private or non-privatelocal area network (LAN), personal area network (PAN), storage areanetwork (SAN), backbone network, global area network (GAN), wide areanetwork (WAN), or collection of any such computer networks such as anintranet, extranet or the Internet (i.e., a global system ofinterconnected network upon which various applications or service runincluding, for example, the World Wide Web). In alternative embodiments,the communication path between the mobile devices 16, between the mobiledevices 16 and the cloud-based service 14 and/or the external computingdevice/system/server 22, may be, in whole or in part, a wiredconnection.

The network 18 may be any network that carries data. Non-limitingexamples of suitable networks that may be used as network 18 includeWi-Fi wireless data communication technology, the internet, privatenetworks, virtual private networks (VPN), public switch telephonenetworks (PSTN), integrated services digital networks (ISDN), digitalsubscriber link networks (DSL), various second generation (2G), thirdgeneration (3G), fourth generation (4G) cellular-based datacommunication technologies, Bluetooth radio, Near Field Communication(NFC), the most recently published versions of IEEE 802.11 transmissionprotocol standards as of June 2015, other networks capable of carryingdata, and combinations thereof. In some embodiments, network 18 ischosen from the internet, at least one wireless network, at least onecellular telephone network, and combinations thereof. As such, thenetwork 18 may include any number of additional devices, such asadditional computers, routers, and switches, to facilitatecommunications. In some embodiments, the network 18 may be or include asingle network, and in other embodiments the network 18 may be orinclude a collection of networks.

As shown, in an aspect of the present invention, data and otherinformation and services are, for example, input by one or more users 15(shown as users 15 a-15 n) and received by one or more associated mobiledevices 16 (shown as mobile devices 16 a-16 n). The mobile devices 16are configured to be communicatively coupled to the cloud-based service14 and/or external device, system or server 22 via the network 18. Inaddition, or alternatively, the mobile devices 16 are configured to becommunicatively coupled to one another via the network 18.

The server 12 is configured to communicate and share data with themobile devices 16 associated with one or more users 15. Accordingly, themobile device 16 may be embodied as any type of device for communicatingwith the server 12 and cloud-based service 14, and/or other user devicesover the network 18. For example, at least one of the user devices maybe embodied as, without limitation, a computer, a desktop computer, apersonal computer (PC), a tablet computer, a laptop computer, a notebookcomputer, a mobile computing device, a smart phone, a cellulartelephone, a handset, a messaging device, a work station, a distributedcomputing system, a multiprocessor system, a processor-based system,and/or any other computing device configured to store and access data,and/or to execute software and related applications consistent with thepresent disclosure.

As will be described in greater detail herein, the server 12 isconfigured to generally provide a means for certain users (users withauthority) to create, modify, or otherwise control distribution of,mobile applications to the mobile devices 16. Accordingly, certain users15 may access the server 12 for the purposes of altering, modifying, orotherwise controlling output of data from the server 12 to other users15 who do not have direct access. For example, in the event the user 15is a client, customer, administrator, or developer associated with theservice provided via the server 12, such a user may have access to oneor more tools for creating, modifying, or controlling a particular apprunning on mobile devices 16. Accordingly, the server 12 is configuredto provide an interface with which such authorized users, such as adeveloper for example, may interact for the purposes of allowing controlover the running app. Upon modifying the app, the authorized user maythen choose to transmit modifications to the app to mobile devices 16for subsequent updates of the app.

As described in greater detail herein, the mobile devices 16 may berunning an abstracted native app thereon, wherein the app allows a user15 to interact and share data with the server 12. The abstracted nativeapp generally includes an app shell, native basic UI elements, and aJSON Translator embedded within the app configured to dynamically and,in real time (when connected to the cloud-based service), translateobjects received from the server 12 (e.g., modifications from authorizeduser) into native UI elements. Accordingly, the JSON Translator acts asa translation layer allowing the dynamic interpretation of data (e.g.,app updates) received from cloud-based service into native UI elementscompatible with the native app running on the device. Thus, the dataexchange format of the present invention allows streaming of UI changes,in contrast to requiring a developer to specifically write the languageinto a compatible format in each instance of an update.

FIG. 2 is a block diagram illustrating the server 12 in greater detail.As shown, the server 12 may include an interface 24, a data collectionand management module 26, an app management system 28, and one or moredatabases 30 for data related one or more users 15 and input receivedtherefrom. For example, the data collection and management module 26 maybe configured to communicate and exchange data with at least the appmanagement system 28 and one or more databases 30, each of which isdescribed in greater detail herein.

As previously described, the interface 24 may generally allow anauthorized user 15 to access data on the server. For example, uponaccessing the server 12 on the cloud-based service 14, the interface 24may be presented to the user via their device 16, in which the user maynavigate a dashboard or standard platform interface so as to access data(stored in the databases 30) collected from other users and theirassociated mobile devices. For example, in the event that the serviceprovided is the crowdsourcing platform, a building owner may access datacollected from persons within the building (e.g., data may includecomfort levels, maintenance issues, movement or location of one or morepersons, etc.), wherein such data may be useful in the maintenance ofcertain systems in the building (e.g., controlling HVAC, alerting propermaintenance worker of any maintenance issues) as we all other usefulinformation, such as identifying which spaces are occupied versus thosespaces which are not occupied, and the like. The interface 24 mayfurther allow an authorized user to access the app management system 28,which is configured to allow a developer or the like to create, modify,or otherwise control output of, the app running on the mobile devices 16of one or more users. The app generally provides an interface on auser's mobile device 16 with which the user may interact to provideuser-driven data to the server 12. Accordingly, the building owner, forexample, may access the app management system 28 and make modificationsto the app when desired (e.g., update the app) and then transmit suchmodifications to mobile devices 16 running the app.

FIG. 3 is a block diagram illustrating at least one embodiment of amobile device 16 for running a native app consistent with the presentdisclosure. The mobile device 16 generally includes a computing system100. As shown, the computing system 100 includes one or more processors,such as processor 102. Processor 102 is operably connected tocommunication infrastructure 104 (e.g., a communications bus, cross-overbar, or network). The processor 102 may be embodied as any type ofprocessor capable of performing the functions described herein. Forexample, the processor may be embodied as a single or multi-coreprocessor(s), digital signal processor, microcontroller, or otherprocessor or processing/controlling circuit.

The computing system 100 further includes a display interface 106 thatforwards graphics, text, sounds, and other data from communicationinfrastructure 104 (or from a frame buffer not shown) for display ondisplay unit 108. The computing system further includes input devices110. The input devices 110 may include one or more devices forinteracting with the mobile device 16, such as a keypad, microphone,camera, as well as other input components, including motion sensors, andthe like. In one embodiment, the display unit 108 may include atouch-sensitive display (also known as “touch screens” or“touchscreens”), in addition to, or as an alternative to, physicalpush-button keyboard or the like. The touch screen may generally displaygraphics and text, as well as provides a user interface (e.g., but notlimited to graphical user interface (GUI)) through which a user mayinteract with the mobile device 16, such as accessing and interactingwith applications executed on the device 16, including the native appconsistent with the present disclosure.

The computing system 100 further includes main memory 112, such asrandom access memory (RAM), and may also include secondary memory 114.The main memory 112 and secondary memory 114 may be embodied as any typeof device or devices configured for short-term or long-term storage ofdata such as, for example, memory devices and circuits, memory cards,hard disk drives, solid-state drives, or other data storage devices.Similarly, the memory 112, 114 may be embodied as any type of volatileor non-volatile memory or data storage capable of performing thefunctions described herein.

In the illustrative embodiment, the mobile device 16 may maintain one ormore application programs, databases, media and/or other information inthe main and/or secondary memory 112, 114. The secondary memory 114 mayinclude, for example, a hard disk drive 116 and/or removable storagedrive 118, representing a floppy disk drive, a magnetic tape drive, anoptical disk drive, etc. Removable storage drive 118 reads from and/orwrites to removable storage unit 120 in any known manner. The removablestorage unit 120 may represents a floppy disk, magnetic tape, opticaldisk, etc. which is read by and written to by removable storage drive118. As will be appreciated, removable storage unit 120 includes acomputer usable storage medium having stored therein computer softwareand/or data.

In alternative embodiments, the secondary memory 114 may include othersimilar devices for allowing computer programs or other instructions tobe loaded into the computing system 100. Such devices may include, forexample, a removable storage unit 124 and interface 122. Examples ofsuch may include a program cartridge and cartridge interface (such asthat found in video game devices), a removable memory chip (such as anerasable programmable read only memory (EPROM), or programmable readonly memory (PROM)) and associated socket, and other removable storageunits 124 and interfaces 122, which allow software and data to betransferred from removable storage unit 124 to the computing system 100.

The computing system 100 further includes one or more applicationprograms 126 directly stored thereon. The application program(s) 126 mayinclude any number of different software application programs, eachconfigured to execute a specific task. For example, as described ingreater detail herein, the application program 126 may include anabstracted native app associated with a service (e.g., crowdsourcingplatform) allowing a user to interact and share data with the server 12.

The computing system 100 further includes a communications interface128. The communications interface 128 may be embodied as anycommunication circuit, device, or collection thereof, capable ofenabling communications between the mobile device 16 external devices(other mobile devices 16, the cloud-based service 14, and the externalcomputing system/server 22). The communications interface 128 may beconfigured to use any one or more communication technology andassociated protocols, as described above, to effect such communication.For example, the communications interface 128 may be configured tocommunicate and exchange data with the server 12, the external computingsystem/server 22 and/or one other mobile device 16 via a wirelesstransmission protocol including, but not limited to, Bluetoothcommunication, infrared communication, near field communication (NFC),radio-frequency identification (RFID) communication, cellular networkcommunication, the most recently published versions of IEEE 802.11transmission protocol standards as of June 2015, and a combinationthereof. Examples of communications interface 228 may include a modem, anetwork interface (such as an Ethernet card), a communications port, aPersonal Computer Memory Card International Association (PCMCIA) slotand card, wireless communication circuitry, etc.

Computer programs (also referred to as computer control logic) may bestored in main memory 112 and/or secondary memory 114 or a localdatabase on the mobile device 16. Computer programs may also be receivedvia communications interface 128. Such computer programs, when executed,enable the computing system 100 to perform the features of the presentinvention, as discussed herein. In particular, the computer programs,including application programs 126, when executed, enable processor 102to perform the features of the present invention. Accordingly, suchcomputer programs represent controllers of computer system 100.

In one embodiment where the invention is implemented using software, thesoftware may be stored in a computer program product and loaded into thecomputing system 100 using removable storage drive 118, hard drive 116or communications interface 128. The control logic (software), whenexecuted by processor 102, causes processor 102 to perform the functionsof the invention as described herein.

In another embodiment, the invention is implemented primarily inhardware using, for example, hardware components such as applicationspecific integrated circuits (ASICs). Implementation of the hardwarestate machine so as to perform the functions described herein will beapparent to persons skilled in the relevant art(s).

In yet another embodiment, the invention is implemented using acombination of both hardware and software.

FIG. 4 is a block diagram illustrating the app management system 28 ingreater detail. As shown, the app management system 28 may include anapp development/modification module 32 and a conversion module 34. Forexample, a user may wish to alter or update the visual format of areport or other visual rendering displayed to a user via the native appon their device. Accordingly, the user will access one or more nativeapp profiles 38(1)-38(n) stored in a native app library 36, in which theuser may modify any one of the native app profiles 38 and subsequentlysave a modified native app into a new profile within the library 36.Thus, at any point, a user may retrieve previous versions of a nativeapp and/or create new versions of a native app so as to provide updates.

The app development/modification module 32 is configured to allow a user(e.g., authorized user) to create, modify, or otherwise control aspectsof a software application that is either currently provided on one ormore mobile devices 16 or will be distributed to one or more mobiledevices 16. The app development/modification module 32 may generallyprovide a software development kit (SDK) or other tools for allowing auser to make any modifications to an app and further transmit suchmodifications to the mobile devices 16 so as to essentially update thenative app running on the mobile device 16, as will be described ingreater detail herein. The modifications may be made according todifferent programming languages, such as JavaScript, HTML, CSS, and thelike. However, the conversion module 34 is configured to receivemodifications from the app development/modification module 32 andfurther convert such modifications into JSON format. For example, theconversion module 34 may include custom, proprietary, known and/orafter-developed data serializing code (or instruction sets) that aregenerally well-defined and operable to receive programming language of afirst type and convert such programming language into a JSON format.

FIG. 5 is a block diagram illustrating streaming of UI changes from theapp management system 28 to a mobile device 16 consistent with thepresent disclosure. As shown, upon making modifications to an app andsubsequent conversion of modification data into JSON objects, the appmanagement system 28 is configured to transmit the JSON objects to amobile device 16 for subsequent updating of a native app running on thedevice 16 based on the JSON objects. As previously described, one ormore of the mobile devices 16 may be running an abstracted native appfor allowing a user 15 to interact and share data with the server 12. Asshown, the abstracted native app generally includes a native appinterface 130, or app shell. The app shell may generally be understoodto be the outermost layer of a program, where shell is another term foruser interface. The mobile device 16 further includes a JSON Translator132 embedded within the app. The JSON translator 132 is configured todynamically and, in real, or near-real, time (when connected to theserver 12), translate objects, namely the JSON objects into native UIelements. Accordingly, the JSON Translator 132 acts as a translationlayer allowing the dynamic interpretation of data (e.g., app updates)received from server 12 into native UI elements compatible with thenative app running on the device 14 and provided via the display unit108.

Thus, the data exchange format of the present invention allows streamingof UI changes, in contrast to requiring a developer to specificallywrite the language into a compatible format in each instance of anupdate. Furthermore, the system allows for changes or modifications tobe made to an app in native form on-the-fly without requiring are-download or an update of the app. In addition, the present inventionmay have applicability to other systems that rely on communicationbetween multiple devices running apps thereon. For example, the abilityto create native mobile application in a manner provided by the presentinvention has tremendous application within Internet of Things (IoT)echo systems by allowing, not only the users to create content, but alsoIoT devices to create/modify content as well, which may inform the usersin real time in their device's native UI of certain events andinformation from the IoT devices and improve their ability to interactand act on this content. Further, the present invention provides theability to still operate based on this content even in an offline mode.

FIGS. 6A-6C illustrate the streaming of app modification data to themobile device and subsequent dynamic interpretation and translation ofapp modification by the translation layer of the mobile device intonative UI elements for display to a user. As shown in FIG. 6A, acustomer (e.g., authorized user) may wish to modify the design (e.g.,interface) of a report that will be displayed to a user via a native apprunning on the user's mobile device. Accordingly, the customer mayaccess the app development/modification module 32 and utilize tools formaking such modifications, where they may chance the format design for areport to be displayed to a user. The conversion module 34 is thenconfigured to receive such modifications and convert them into JSONobject(s). For example, the conversion module 34 may break the formatdown into widgets and then serialize into JSON objects. Referring toFIG. 6B, the JSON object(s) may then be transmitted to the mobile device16 running the native app, at which point, the JSON object(s) are thendecoded back into native UI elements via the translation layer (JSONTranslator 132) and displayed on the display of the device 14 (FIG. 6C).

FIG. 7 is a block diagram illustrating one embodiment of a systemarchitecture consistent with the present disclosure. The architectureillustrated in FIG. 7 may provide the same or similar functions aspreviously described herein, namely the JSON data exchange format foruse with a native app running on a user's mobile device, wherein theexchange format is configured to improve user experience and interactionwith the app.

As used in any embodiment herein, the term “module” may refer tosoftware, firmware and/or circuitry configured to perform any of theaforementioned operations. Software may be embodied as a softwarepackage, code, instructions, instruction sets and/or data recorded onnon-transitory computer readable storage medium. Firmware may beembodied as code, instructions or instruction sets and/or data that arehard-coded (e.g., nonvolatile) in memory devices. “Circuitry”, as usedin any embodiment herein, may comprise, for example, singly or in anycombination, hardwired circuitry, programmable circuitry such ascomputer processors comprising one or more individual instructionprocessing cores, state machine circuitry, and/or firmware that storesinstructions executed by programmable circuitry. The modules may,collectively or individually, be embodied as circuitry that forms partof a larger system, for example, an integrated circuit (IC), systemon-chip (SoC), desktop computers, laptop computers, tablet computers,servers, smart phones, etc.

Any of the operations described herein may be implemented in a systemthat includes one or more storage mediums having stored thereon,individually or in combination, instructions that when executed by oneor more processors perform the methods. Here, the processor may include,for example, a server CPU, a mobile device CPU, and/or otherprogrammable circuitry.

Also, it is intended that operations described herein may be distributedacross a plurality of physical devices, such as processing structures atmore than one different physical location. The storage medium mayinclude any type of tangible medium, for example, any type of diskincluding hard disks, floppy disks, optical disks, compact diskread-only memories (CD-ROMs), compact disk rewritables (CD-RWs), andmagneto-optical disks, semiconductor devices such as read-only memories(ROMs), random access memories (RAMs) such as dynamic and static RAMs,erasable programmable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), flash memories, Solid StateDisks (SSDs), magnetic or optical cards, or any type of media suitablefor storing electronic instructions. Other embodiments may beimplemented as software modules executed by a programmable controldevice. The storage medium may be non-transitory.

As described herein, various embodiments may be implemented usinghardware elements, software elements, or any combination thereof.Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, appearances of the phrases “in oneembodiment” or “in an embodiment” in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

The terms and expressions which have been employed herein are used asterms of description and not of limitation, and there is no intention,in the use of such terms and expressions, of excluding any equivalentsof the features shown and described (or portions thereof), and it isrecognized that various modifications are possible within the scope ofthe claims. Accordingly, the claims are intended to cover all suchequivalents.

INCORPORATION BY REFERENCE

References and citations to other documents, such as patents, patentapplications, patent publications, journals, books, papers, webcontents, have been made throughout this disclosure. All such documentsare hereby incorporated herein by reference in their entirety for allpurposes.

EQUIVALENTS

Various modifications of the invention and many further embodimentsthereof, in addition to those shown and described herein, will becomeapparent to those skilled in the art from the full contents of thisdocument, including references to the scientific and patent literaturecited herein. The subject matter herein contains important information,exemplification and guidance that can be adapted to the practice of thisinvention in its various embodiments and equivalents thereof.

What is claimed is:
 1. A system for providing cross-device native functionality for a native app, the system comprising: a mobile device for user input and interaction, the mobile device running a native application thereon; and a server configured to communicate with and exchange data with the mobile device and provide one or more modifications to the native application; wherein the mobile device comprises a processor coupled to a memory containing instructions executable by the processor to cause the mobile device to: receive, from the server, modification data associated with a modification to the native application; translate the modification data into native user interface (UI) elements; and display the native UI elements to a user associated with the mobile device.
 2. The system of claim 1, wherein the mobile device is selected from the group consisting of a tablet computer, a laptop computer, a notebook computer, a mobile computing device, a smart phone, and a cellular telephone.
 3. The system of claim 1, wherein the server and the mobile device are configured to wirelessly communicate and exchange data with one another over a network.
 4. The system of claim 3, wherein the network is selected from the group consisting of Wi-Fi wireless data communication technology, the internet, private networks, virtual private networks (VPN), public switch telephone networks (PSTN), integrated services digital networks (ISDN), digital subscriber link networks (DSL), various second generation (2G), third generation (3G), fourth generation (4G) cellular-based data communication technologies, Bluetooth radio, and Near Field Communication (NFC).
 5. The system of claim 1, wherein the communication and exchange of data between the server and the mobile device is provided via a cloud-based service.
 6. The system of claim 5, wherein the cloud-based service comprises a crowdsourcing platform.
 7. The system of claim 6, wherein the native application running on the mobile device allows a user to provide user-driven data to the crowdsourcing platform, wherein the user-driven data is associated with an environment in which the user is located.
 8. The system of claim 7, wherein the user-driven data is associated with user comfort within a given environment in which the user is located.
 9. The system of claim 8, wherein the user comfort is associated with temperature within the given environment.
 10. The system of claim 1, wherein the native application is an abstracted native application.
 11. The system of claim 10, wherein the abstracted native application comprises an application shell, native basic UI elements, and a JSON Translator embedded within the application.
 12. The system of claim 11, wherein the JSON Translator is a translation layer configured to allow dynamic interpretation of data received from the server into native UI elements compatible with the native application running on the mobile device.
 13. The system of claim 11, wherein the JSON Translator is configured to dynamically and in real, or near-real, time translate modification data objects into native UI elements.
 14. The system of claim 13, wherein the modification data objects comprise JSON objects converted from initial modification data objects created based on one or more non-JSON format programming languages.
 15. The system of claim 13, wherein the one or more non-JSON format programming languages are selected from the group consisting of HTML, CSS, and the like.
 16. The system of claim 1, wherein the modification data comprises one or more changes or modifications to the native application from an administrator of the native application. 